|
|
A flight plan (FPL)
shall be submitted in accordance with RAP 91.210
prior to every flight.
Prior to the departure of a flight:
|
|
|
1.1.
The pilot in command of the aircraft will ensure of have knowledge of
all the aeronautical information available, regardless of the planned flight (IFR or VFR) and must analyze the AIS information and meteorological forecast, the information about natural and artificial obstacles, the plotting on the relevant cartography of the projected flight route, the NOTAM information that affects the flight, maneuvering and military training areas, air defense identification zone (ADIZ), the necessary fuel calculation, and the preparation of the plan to follow in case the flight cannot be completed exactly as planned.
|
|
|
1.2.
The Flight plan submission and approval do not exempt compliance with the requirements
demanded by other national authorities such as customs, migration, health control, judicial, police, taxes, etc.
|
|
|
1.3.
When the projected flight is intended to carry out operations along a route or in an area where a navigation specification is prescribed, they will be responsible for ensuring the appropriate RNP approval and that they meet the conditions applicable for approval.
|
|
|
1.4.
Approval required for RVSM will be ensured under conditions of operations in Reduced Vertical Separation Minimum (RVSM) airspace.
|
2
REQUIREMENTS FOR SUBMIT A FLIGHT PLAN
|
|
|
2.1.
According RAP 91 - FLIGHT RULES AND GENERAL OPERATION, take under consideration:
|
|
|
2.1.1.
The information
regarding the planned flight, or part of it, must be provided to ATC in the flight plan format in force as of 2022 (Doc. 4444).
|
|
|
2.1.2.
A flight plan shall be submitted prior:
-
Any IFR/VFR flight from or to an aerodrome, runway, or heliport in a Control Area (CTR)
-
Any IFR/VFR flight crossing controlled air spaces.
-
Any flight or portion thereof providing air traffic control service.
-
Any IFR flight within the airspace with advisory service.
-
Any flight within designated areas or along designated routes when so required by the appropriate ATS authority to facilitate the provision of alerting and search and rescue services.
-
Any flight within designated areas or along designated routes when so required by the appropriate ATS authority to facilitate the coordination with appropriate military units or air traffic services units in adjacent States, in order to avoid the possible need for interception for identification.
-
Any flight through international boundaries.
|
|
|
2.2.
Foreign
government aircraft, national government entities, and military aircraft must comply with the requirement to submit a flight plan for all operations.
|
3
SUBMISSION OF FLIGHT PLAN
|
The flight plan proposal must be submitted to the
corresponding AIS office, Station and/or area in charge of reception, in the following ways:
|
3.1
PLACE AND WAY OF SUBMISSION
|
3.1.1
SUBMISSION OF A FLIGHT PLAN AT AN AERODROME WITH AN AIS/ARO OFFICE
|
It is mandatory to file the flight plan (FPL) prior to departure, as well as the corresponding associated delay (DLA), change (CHG) or cancellation (CNL) messages, as follows:
-
Via AMHS/AFTN SYSTEM: Procedure (Direct Filing) for air operators wishing to transmit flight plans and their associated messages, upon request and approval of the AIA CHIEF. AIC 09/2018.
-
Via EMAIL: Flight plans will be sent to the emails aislima@corpac.gob.pe, aislimaperu@gmail.com, with the flight plan format and with the correct data to be inserted.
-
Via PHYSICAL-PAPER: The flight plan proposal will be submitted to the AIS/AD office of the departure aerodrome in the ICAO format.
-
By TELEPHONE: As long as you have the CADAS AMHS U/S, FDD U/S or NO EMAIL AVAILABLE, with charge to be regularized.
-
AFIL: The flight plan submitted from the air (AFIL) will be only and exclusively for aircraft in flight. This flight plan will contain the essential data regarding the flight or part of the flight to be performed, including: aircraft identification, flight rules, aircraft type, departure aerodrome, departure time, speed, level, route, destination aerodrome, estimated elapsed time, alternate aerodrome, endurance, persons on board, color, marking, and model of the aircraft, pilot in command and license. The TWR or ACC personnel, receiving a flight plan by frequency, shall transcribe it in the corresponding format and dictate by the established means (ATS) to the corresponding FDP unit, verifying all the data required in this document. The word AFIL shall be inserted in item 13 indicating in ITEM 18 of the FPL the descriptor DEP/ with the code of the unit originating the flight plan.
|
3.1.2
SUBMISSION OF A FLIGHT PLAN AT AN AERODROME WITHOUT AIS/ARO OFFICE
|
At aerodromes where there is no ARO OFFICE, the tasks of this unit will be assigned to the person who assumes the functions, for which the flight plan submission will be performed:
-
In person at the operations offices or any other unit of the air navigation services.
-
The Air Traffic Services, will accept only by the appropriate radio frequency; the flight plans (AFIL) of the aircraft that take-off from the runways or uncontrolled aerodromes in which there is no technical operative personnel of the Air Navigation Services, as long as the flight does not intend to enter a controlled airspace.
-
When there is no ATS unit at the aerodrome of arrival, the notice of arrival shall be given to the nearest ATC unit, or to the aeronautical station serving the ATS unit in charge of the FIR in which the aircraft operates or to a designated ATS notification office. Failure by the pilot to comply with these provisions, especially with regard to the notice of arrival (ARR), may result in unnecessary search and rescue operations.
Failure by the pilot to comply with these provisions, especially with regard to the notice of arrival (ARR), may result in unnecessary search and rescue operations.
|
3.2
FLIGHT PLAN RECEPTION
|
The FPL shall be received at least 60 minutes prior to each flight departure
and shall not be submitted more than 120 hours prior to the estimated off-block time of a flight by air operators, armed forces and police (FAP, INP, EP and PNP) via AMHS/AFTN (prior Letter of Agreement), e-mail or physical, if not possible via telephone or other digital means.
|
3.3
FLIGHT PLAN VERIFICATION
|
The AIS/ARO Specialist or Aeronautical Specialist will verify if the FPL is correctly filled out, considering the following:
-
Verify and analyze if the FPL form (items 7 to 19) contain the correct data.
-
Verify if in the Aeronautical Information Products (PIA) there is any relevant information for the projected flight.
-
Verify the respective authorization of the operation through RD, PVI, PVN, PVC, PEV, MCA.
-
Verify the pilot's authorization in the DGAC system.
-
In the case of a private flight, verify with the CORPAC S.A. Invoicing Area if the company has paid for the operation, in order to accept the Flight Plan, as appropriate.
-
If any observations are found in the FPL, the AIS/ARO Specialist or aeronautical specialist shall advise the pilot or company representative, in accordance with the relevant Aeronautical Regulations, ICAO documents and Letter Agreements to amend it, as follows:
f.1.- coordinate with the representative who shall forward the corrected flight plan for acceptance.
|
3.4
FLIGHT PLAN ACCEPTANCE
|
The AIS/ARO Specialist or aeronautical specialist shall accept the FPL, via acknowledgement of receipt (ACK) or respective stamp, which shall bear the date and UTC time of receipt.
|
3.5
FLIGHT PLAN TRANSMISSION
|
-
Transmit the FPL through the CADAS/AMHS or FDD Terminal considering the AFTN addresses, as appropriate.
-
File the FPL Form physically or digitally, as appropriate.
|
|
|
Flight plans shall not be submitted more than 120 hours in advance of the estimated off-block time (EOBT) and at least 60 minutes prior to departure for international flights (IFR or VFR), taking into account timely information to the ATS units in the airspace along their route, including the requirements for air traffic flow (ATFM).
For any changes to the submitted flight plan, the corresponding ATS unit shall be notified as soon as possible. In case of delay (DLA) of 30 minutes or more in the departure of a flight for which a flight plan has been submitted, the flight plan will be amended, or a new one
will be submitted after cancellation of the previous plan.
|
|
|
The flight plan will contain information regarding the following concepts that the appropriate
authority deems relevant:
-
Aircraft identification;
-
Flight rules and types;
-
Number and types of aircraft and wake turbulence category;
-
Equipment;
-
Departure Aerodrome;
-
Estimated off-block time;
-
Cruising speed;
-
Cruising level;
-
Route to be followed;
-
Destination aerodrome and total estimated elapsed time;
-
Alternate aerodrome;
-
Endurance;
-
Total number of persons on board;
-
Emergency and survival equipment; and
-
Other information.
|
ITEM 7: AIRCRAFT IDENTIFICATION (MAXIMUM 7 CHARACTERS)
|
ENTER one of the following aircraft identifications, not exceeding the 7
alphanumeric characters and without hyphens, spaces
or symbols:
-
The ICAO designator for the aircraft operating agency followed by the flight identification (e.g. LAN531, NGA213, JTR25) when the radiotelephony call sign to be used by the aircraft will consist of the ICAO telephony designator for the operating agency followed by the flight identification
(e.g. KLM511, NIGERIA 213, JESTER 25);
-
The nationality or common mark and the registration marks of the aircraft;
e.g. OB-2024P, EIAKO, 4XBCD, N2567GA, when:
b.1
The radiotelephony call sign to be used by the aircraft will consist in this identification (e.g. CGAJS), or when is preceded by the ICAO telephony designator for the aircraft operating agency (e.g CGAJS);
b.2
The aircraft is not equipped with radio;
Note1:
Standards for nationality, common and registration marks to be used as contained in Annex 7, numeral 3.
Note2:
Provisions for the use of radiotelephony call signs are contained in Annex
10, volume
II, chapter
5. ICAO designators for aircraft operating agencies are contained in Doc
8585 - Designators for Aircraft Operating Agencies, Aeronautical Authorities and Services.
Note3:
Provisions for the use of radiotelephony call signs that exceed 7 (seven) characters require the pilot to enter the identification with the alphanumeric characters (letters and numbers) until complete 7
and in item 18
the pilot should enter the designator RMK/ followed by the complete call sign
that must be used, followed by REG/ indicating only one aircraft registration mark or another official mark designator detailing the rest of the registration marks in item
18 under the designator RMK/,
as mentioned above.
|
ITEM 8: FLIGHT RULES AND TYPES (ONE OR TWO CHARACTERS)
|
a) Flight rules (1 character)
|
ENTER one of the following letters to denote the category of flight rules with which the pilot intends to comply.
-
I -
when the whole flight will be under
IFR
;
-
V -
when the whole flight will be under
VFR
;
-
Y -
for IFR first, then followed by one or more subsequent changes of flight rules; or
-
Z -
for VFR first, then followed by one or more subsequent changes of flight rules.
Note:
In the case of using Y or Z, the pilot must enter, in item
15, the point or points where a
change of flight rules is planned.
|
b) Flight type (1 character)
|
ENTER one of the following letter to indicate the flight plan type:
-
S -
for scheduled air service;
-
N -
for non-scheduled air service;
-
G
- for general aviation;
-
M -
for military; or
-
X
- for other than the preceding categories.
Note:
Specify status of a flight following the indicator STS in Item 18, or when necessary to denote other reasons for specific handling by ATS, indicate the reason following the indicator RMK in Item 18.
|
ITEM 9: NUMBER AND TYPE OF AIRCRAFT AND WAKE TURBULENCE CATEGORY
|
a)
Aircraft Number (1 or 2
characters)
|
ENTER the number of aircraft,
in case of formation flights.
|
b) Aircraft type (2 to 4 characters)
|
ENTER the appropriate designator as specified in ICAO Doc. 8643,
"Aircraft Type Designators".
Note
: If
no such designator has been assigned, or in case of formation flights comprising more than one aircraft
type, enter ZZZZ, and specify in Item 18, the number and)
type(s) of aircraft preceded by TYP/ aircraft type and REG/ one aircraft registration mark or other official mark designator.
Detailing the rest of the mark records in item 18 under the designator RMK/, mentioned above.
|
c)
Wake turbulence category (1 character)
|
ENTER an
oblique stroke followed by one of the following letters to indicate the wake turbulence category of the aircraft:
-
J -
SUPER, to indicate a specific aircraft type, as in Aircraft Type Designators (ICAO DOC. 8643);
-
H -
HEAVY, to indicate an aircraft type with a maximum certificated take-off mass of 136, 000 Kg or more, except aircraft type indicated in Doc. 8643 within SUPER (J) category;
-
M -
MEDIUM, to indicate an aircraft type with a maximum certificated take-off mass of less than 136,000 Kg but more than 7,000 Kg; and
-
L -
LIGHT, to indicate an aircraft type with a maximum certificated take-off mass of 7,000 Kg or less.
|
ITEM 10: EQUIPMENT AND CAPABILITIES
|
Capabilities comprise the following elements:
-
Presence of appropriate equipment on board the aircraft;
-
Equipment and capabilities commensurate with flight crew qualifications; and
-
when applicable, the authorization from the appropriate authority.
|
Radio communication, navigation and approach aid equipment capabilities,
|
ENTER one letter, as follows:
-
N
- if no COM/NAV/approach aid equipment is carried for the considered route, or the equipment is not in service.
-
S
- if COM/NAV/ approach aid equipment is carried for the considered route and the equipment is functioning (see Note 1); and/or,
ENTER one or more of the following letters to indicate the serviceable COM/NAV/approach aid equipment and capabilities available:
|
|
|
|
LETRA /
LETTER
|
EQUIPO Y CAPACIDADES /
EQUIPMENT AND CAPABILITIES
|
|
A
|
Sistema de aterrizaje GBAS /
GBAS landing system
|
|
B
|
LPV (APV con /
with
SBAS)
|
|
C
|
LORAN
C
|
|
D
|
DME
|
|
E1
|
FMC WPR
ACARS
|
|
E2
|
D-FIS
ACARS
|
|
E3
|
PDC
ACARS
|
|
F
|
ADF
|
|
G
|
GNSS (véase la Nota 2) /
(see Note 2)
|
|
H
|
HF
RTF
|
|
I
|
Navegación inercial
/
Inertial navigation
|
|
J1
|
CPDLC ATN VDL Modo /
Mode
2 (véase la Nota 3) /
(see Note 3)
|
|
J2
|
CPDLC FANS 1/A
HFDL
|
|
J3
|
CPDLC FANS 1/A VDL Modo 4 /
Mode 4
|
|
J4
|
CPDLC FANS 1/A VDL Modo 2 /
Mode 2
|
|
J5
|
CPDLC FANS 1/A SATCOM
(INMARSAT)
|
|
J6
|
CPDLC FANS 1/A SATCOM
(MTSAT)
|
|
J7
|
CPDLC FANS 1/A SATCOM
(Iridium)
|
|
K
|
(MLS)
|
|
L
|
ILS
|
|
M1
|
ATC RTF SATCOM
(INMARSAT)
|
|
M2
|
ATC RTF
(MTSAT)
|
|
M3
|
ATC RTF
(Iridium)
|
|
O
|
VOR
|
|
P1-P9
|
Reservado para RCP /
Reserved for RCP
|
|
R
|
PBN aprobada /
approved
(véase la Nota 4) /
(see Note 4)
|
|
T
|
TACAN
|
|
U
|
UHF
RTF
|
|
V
|
VHF
RTF
|
|
W
|
RVSM aprobada /
approved
|
|
X
|
MNPS aprobada /
approved
|
|
Y
|
VHF con capacidad de separación de canales de /
channel spacing capability of
8,33 kHz
|
|
Z
|
Demás equipo instalado a bordo u otras capacidades(véase la Nota 5) /
Other equipment carried on board or other capabilities (see Note 5)
|
|
Any alphanumeric characters not indicated above are reserved.
Note 1:
If the letter “S” is used, standard equipment is considered to be VHF RTF, VOR, and ILS, unless another combination is prescribed by the appropriate ATS authority.
Note 2:
If the letter “G” is used, the types of external GNSS augmentation, if any, are specified in Item 18 following the indicator NAV/ and separated by a space.
Note 3:
See RTCA/EUROCAE Interoperability Requirements Standard for ATN Baseline 1 (ATN B1 INTEROP Standard - DO-280B/ED-110B) for data link services/ air traffic control clearance and information/air traffic control communications management/air traffic control microphone check.
Note 4:
If the letter “R” is used, the performance-based navigation levels that can be met are specific in Item 18 following the indicator PBN/. Maximum 8;
if more than 8 indicators remain, identify those considered less relevant to the flight and insert them in item 18 of the NAV/. For any PBN capability: If "all sensors" or GNSS are on file then "G" must be present in item 10a; If "all sensors" or DME / DME are on file then "D" must be present in item 10a; If "all sensors" or INS / IRU are on file then "I" must be present in item 10a; If DME / DME / IRU is on file then "D" and "I" must be present in item 10a.
Note 5:
If the letter “Z” is used, specify in Item 18 the other equipment or capabilities carried on board, preceded by COM/, NAV/, and/or DAT, as appropriate.
Note 6:
Information on navigation capability is provided to ATC for clearance and routing purposes.
Note 7:
Guidance on the application of
performance-based communication, which prescribes RCP to an air traffic service in a specific area, is contained in the performance-based Communication and Surveillance (PBCS) Manual (Doc 9869).
|
Surveillance
Equipment and Capabilities
|
ENTER
N
if no surveillance equipment for the route to be flown is carried, or the equipment is unserviceable;
or,
ENTER one or more of the following descriptors, to a maximum of 20 characters, to describe the serviceable surveillance equipment and/or capabilities on board:
|
|
|
-
A
Transponder -- Mode A (4 digits - 4096 codes)
-
C
Transponder -- Mode A (4 digits - 4096 codes) and Mode C
|
|
|
-
E
Transponder -- Mode S, including aircraft identifications, pressure-altitude, and extended squitter (ADS-B) capability.
-
H
Transponder -- Mode S, including aircraft identification, pressure-altitude and enhanced surveillance capability.
-
I
Transponder -- Mode S, including aircraft identification, but no pressure-altitude capability.
-
L
Transponder -- Mode S, including aircraft identification, pressure-altitude, extended squitter (ADS-B) and enhanced surveillance capability.
-
P
Transponder -- Mode S, including pressure altitude, but no aircraft identification capability.
-
S
Transponder -- Mode S, including both pressure altitude and aircraft identification capability.
-
X
Transponder -- Mode S with neither aircraft identification nor pressure-altitude capability.
Note:
- Enhanced surveillance capability is the ability of the aircraft to down-link aircraft derived data via a Mode S transponder.
|
|
|
-
B1
ADS-B with dedicated 1090 MHz ADS-B “out” capability
-
B2
ADS-B with dedicated 1090 MHz ADS-B “out” and “in” capability
-
U1
ADS-B “out” capability using UAT
-
U2
ADS-B “out” and “in” capability using UAT
-
V1
ADS-B “out” capability using VDL Mode 4
-
V2
ADS-B “out” and “in” capability using VDL Mode 4
|
|
|
-
D1
ADS-C with FANS 1/A capabilities
-
G1
ADS-C with ATN capabilities
Alphanumeric characters not indicated above are reserved.
E.g. ADE3RV/HB2U2V2G1
Note 1
.- The required surveillance performance specification(s) (RSP), if applicable, shall be listed in item 18 after the SUR/ indicator.
The Performance-Based Communication
and Surveillance (PBCS) Manual (Doc. 9869) contains guidance texts on the application of performance based surveillance prescribing RSP for an air traffic service in a specific area.
Note 2
.- In item 18, after the SUR/ indicator, as required by the appropriate ATS authority, additional surveillance equipment or capabilities shall be listed.
|
ITEM 13: DEPARTURE AERODROME AND TIME
|
a) Departure Aerodrome (4 characters)
|
ENTER the ICAO four-letter location indicator of the departure aerodrome as specified in Doc 7910, Location Indicators, or GEN 2.4 Part (Peru
AIP).
E.g. SPJC
If no location indicator has been assigned,
ENTER ZZZZ and specify, in Item 18, preceded by DEP/, coordinates or,
by bearing and distance regarding a significant point and RMK/ in plain text the name of the place of
departure.
E.g.
DEP/ITAYA
or, if the flight plan is received from an aircraft in flight,
ENTER AFIL, and specify, in Item 18, the ICAO four-letter location indicator of the ATS unit from which supplementary flight plan data can be obtained, preceded by DEP/.
|
|
|
ENTER for a flight plan submitted before departure, the estimated off-block time (EOBT), or, for a flight plan received from an aircraft in flight, the actual or estimated time over the first point of the route to which the flight plan applies.
|
|
|
ENTER the cruising speed
and the first cruising level as in (b), without a space between them,
following the arrow, enter the route description.
|
a)
Cruising speed (maximum 5 characters)
|
ENTER the True airspeed for the first or the whole cruising portion of the flight, in terms of:
-
Or Knots, expressed as N followed by 4 figures
(e.g. N0480),
-
Or true Mach number, expressed as M followed by 3 figures
(e.g. M082).
|
b)
Cruising level (maximum 5 characters)
|
ENTER the planned cruising level for the first or the whole portion of the route to be flown, in terms of:
-
Flight level, expressed as F followed by 3 figures
(e.g.
F370).
-
Altitude in hundreds of feet, expressed as A followed by 3 figures
(e.g. A055).
|
c)
Route (including changes of speed, level and/or flight rules),
|
Flights along designated ATS routes
ENTER , if the departure aerodrome is located on or connected to the ATS route, the designator of the first ATS route.
E.g. W23.
Note
: If the aerodrome has Standard Instrument Departures (SID) or Standard Instrument Arrivals (STAR), it is mandatory to enter the coded designator of the respective SID or STAR.
Example: TELE1F ATATU UM674.
or, ENTER the letters DCT followed by
the point of joining the first ATS route, followed by the ATS route designator; if the departure aerodrome is not on or connected to the ATS route.
Example: DCT BUTUX DCT.
Then, enter
each point at which either a change of speed and/or level,
or a change of ATS route
and/or flight rules is planned to commence.
Note
. When a transition is planned between a lower and upper ATS route and the routes are oriented in the same direction, the point of transition need not be inserted.
Followed in each case;
- by the designator of the next ATS route segment, even if the same as the previous one,
- or by DCT, if the flight to the next point will be outside a designated route, unless both points are defined by geographical coordinates.
Flights outside designated ATS routes
ENTER points normally not more than 30 minutes flying time or 370 km (200 NM) apart, including each point at which a change of speed or level, a change of track, or a change of flight rules is planned.
Or, when required by appropriate ATS authorities.
DEFINE the track of flights operating predominantly in an east-west direction between 70°N and 70°S by reference to significant points formed by the intersections of
parallels of latitude of
whole or half degrees with longitude. For flights operating in areas outside those latitudes
spaced at intervals of 10 degrees of latitude ,
the tracks shall be defined by significant points formed by the intersection of parallels of latitude with meridians normally spaced at 20 degrees of longitude. The distance between two significant points shall, as far as possible, not exceed one hour’s flight time. Additional significant points shall be established as deemed necessary. For flights operating predominantly in a north-south direction, define tracks by reference to significant points formed by the intersection of whole degrees of longitude with specified parallels of latitude which are spaced at 5 degrees.
ENTER DCT between successive points unless both points are defined by geographical coordinates or by bearing and distance.
USE ONLY the conventions in (1) to (5) below and SEPARATE each sub-item by a space.
|
1. ATS route (2 to 7 characters)
|
The coded designator assigned to the route or route segment including, where appropriate, the coded designator assigned to the standard departure (SID) or arrival route (STAR).
Example:
ITAV2F, TELE1F.
|
2.
Significant point (2 to 11 characters)
|
The coded designator (2 to 5 characters) assigned to the point.
Example: REKEM, KOSKO
If no coded designator has been assigned, one of the following ways:
a) Degrees only (7 characters):
2 figures describing latitude in degrees, followed by “N” (North) or “S” (South), followed by 3 figures describing longitude in degrees, followed by “E” (East) or “W” (West). Make up the correct number of figures, where necessary, by insertion of zeros.
Example:
0646S07949W.
b) Degrees and minutes (11 characters):
4 figures describing latitude in degrees and tens and units of minutes followed by “N” (North) or “S” (South), followed by 5 figures describing longitude in degrees and tens and units of minutes, followed by “E” (East) or “W” (West). Make up the correct number of figures, where necessary, by insertion of zeros.
Example: 0618S08058W.
c) Bearing and distance from a significative
reference
point:
The identification of a significative point
followed by the bearing
from the point in the form of 3 figures giving degrees magnetic, followed by the distance from the point in the form of 3 figures expressing nautical miles. In areas of high latitude where it is determined by the appropriate authority that reference to degrees magnetic is impractical, degrees true may be used. Make up the correct number of figures, where necessary, by insertion of zeros.
Example:
A
point 180° magnetic at a distance of 40 nautical miles from "URC" VOR
should be expressed as URC180040.
|
3.
Change of speed or level (maximum 21 characters)
|
The point at which a change of speed (5% TAS or 0.01 Mach or more) or a change of level is planned to commence, expressed exactly as in (2) above, followed by an oblique stroke and both the cruising speed and the cruising level, expressed exactly as in
(a) and (b) above, without a space between them, even when only one of these quantities will be changed.
Examples:
LN/N0284A045 TAP/N0190F250 MIPAS/N0420F320 1552S07232W/N0450F350 46N078W/M082F330 URC180040/N0350M0840
|
4.
Change of flight rules (maximum 3 characters)
|
The point at which the change of flight rules is planned, expressed exactly as in (2) or (3) above as appropriate, followed by a space and one of the following:
-
VFR if from IFR to VFR
-
IFR if from VFR to IFR.
Examples: PADIS VFR PADIS/N0284A050 IFR
|
5.
Cruise climb (maximum 28 characters)
|
The letter C followed by an oblique stroke; THEN the point at which cruise climb is planned to start, expressed exactly as in (2) above, followed by an oblique stroke; THEN the speed to be maintained during cruise climb, expressed exactly as in (a) above, followed by the two levels defining the layer to be occupied during cruise climb, each level expressed exactly as in (b) above, or the level above which cruise climb is planned followed by the letters PLUS, without a space between them:
Examples
:
-
C/12S075W/M082F290F350
-
C/12S075W/M082F290PLUS
-
C/52S075W/M220F580F620.
|
ITEM 16: DESTINATION AERODROME AND TOTAL ESTIMATED ELAPSE TIME, DESTINATION ALTERNATE AERODROMES
|
Destination aerodrome and total estimated elapsed time (8 characters)
|
ENTER the ICAO four-letter location indicator of the destination aerodrome as specified in ICAO Doc 7910, Location Indicators, then
followed, without
space, by the total
estimat
ed elapsed of the flight.
Example:
SPJC0245
Or, if no location indicator has been assigned,
ENTER ZZZZ, followed by the total
estimated elapsed of the flight and specify in Item 18,
preceded by DEST/ coordinates or bearing and
distance regarding
a significant point and RMK/ in plain text the name of the place of arrival.
Example:
ZZZZ0035
-
DEST/0125S07543W RMK/LA CALERA
-
DEST/PULTU08074 RMK/RIO ABIERTO
Note
: - For a flight plan received from an aircraft in flight, the total estimated elapsed time is the estimated time from the first point of the route to
which the flight plan applies to the termination point of the flight plan.
|
Destination alternate aerodromes
|
ENTER the ICAO four-letter location indicator(s) of not more than two destination alternate aerodromes, as specified in ICAO Doc 7910, Location Indicators, separated by a space.
Example: SPJC SPZO
Or,
ZZZZ and specify in Item 18, preceded by ALTN/ coordinates or
bearing and
distance regarding
a significant point and RMK/ in plain text the name of the destination alternate aerodrome(s)
Example:ZZZZ
-
ALTN/063S07543W RMK/LOS LOSBOS
-
ALTN/TOC063050 RMK/TOCTO
Note:
Airlines operating to the United States and intending to apply exceptions for filing in the destination alternate aerodrome should enter "ZZZZ" in item 16 of the FPL and specify ALTN/NIL in item 18.
|
ITEM 18: OTHER INFORMATION
|
Note:
Use of indicators not included under this item may result in data being rejected, processed incorrectly or lost.
Hyphens or oblique strokes should only be used as prescribed below.
ENTER 0 (zero) if no other information,
or, any other necessary information in the sequence shown hereunder, in the form of the appropriate indicator selected from those defined hereunder followed by an oblique stroke and the information to be recorded:
STS:
Reason for special handling by ATS, e.g,
a search and rescue mission, as follows:
-
ALTRV
: for a flight operated in accordance with an altitude reservation;
-
ATFMX
: for a flight approved for exemption from ATFM; measures by the appropriate ATS authority;
-
RFF
: fire-fighting;
-
FLTCK
: flight check for calibration of navaids;
-
HAZMAT
: for a flight carrying hazardous material;
-
HEAD
: a flight with Head of State status;
-
HOSP
: for a medical flight declared by medical authorities;
-
HUM
: for a flight operating on a humanitarian mission;
-
MARSA
: for a flight for which a military entity assumes responsibility for separation of military aircraft;
-
MEDEVAC
: for a life critical medical emergency evacuation;
-
NONRVSM
: for a non-RVSM capable flight intending to operate in RVSM airspace;
-
SAR
: for a flight engaged in a search and rescue mission; and
-
STATE
: for a flight engaged in military, customs, or police services.
Other reasons for special handling by ATS shall be denoted under the designator RMK/.
Note
: Fraudulent use of these designators may be considered a serious breach of procedures with the legal consequences established for such cases by the applicable provisions. Including disciplinary or sanctioning measures, if applicable.
PBN
/ Indication of RNAV and/or RNP capabilities. Include as many of the descriptors below, as apply to the flight, up to a maximum of
8 entries, i.e. a total of not more than 16 characters.
|
|
|
ESPECIFICACIONES RNAV
/
RNAV
SPECIFICATIONS
|
|
A1
|
RNAV 10 (RNP 10) |
|
B1
|
RNAV 5, todos los sensores permitidos
/
all permitted sensors
|
|
B2
|
RNAV 5 GNSS |
|
B3
|
RNAV 5 DME/DME |
|
B4
|
RNAV 5 VOR/DME |
|
B5
|
RNAV 5 INS o IRS |
|
B6
|
RNAV 5 LORANC |
|
C1
|
RNAV 2, todos los sensores permitidos
/
all permitted sensors
|
|
C2
|
RNAV 2 GNSS |
|
C3
|
RNAV 2 DME/DME |
|
C4
|
RNAV 2 DME/DME/IRU |
|
D1
|
RNAV 1, todos los sensores permitidos
/
all permitted sensors
|
|
D2
|
RNAV 1 GNSS |
|
D3
|
RNAV 1 DME/DME |
|
D4
|
RNAV 1 DME/DME/IRU |
|
|
ESPECIFICACIONES RNP
/
RNP SPECIFICATIONS
|
|
L1
|
RNP 4 |
|
O1
|
RNP 1 básica, todos los sensores permitidos
/
Basic RNP 1
all permitted sensors
|
|
O2
|
RNP 1 GNSS básica
/
basic
|
|
O3
|
RNP 1 DME/DME básica
/
basic
|
|
O4
|
RNP 1 DME/DME/IRU básica
/
basic
|
|
S1
|
RNP APCH |
|
S2
|
RNPAPCH con
/
with
BARO-VNAV
|
|
T 1
|
RNP AR APCH con
/
with
RF (se requiere autorización especial)
/
(special authorization required)
|
|
T 2
|
RNP AR APCH sin
/
without
RF (se requiere autorización especial)
/
(special authorization required)
|
|
Combinations of alphanumeric characters not indicated above are reserved.
NAV/
Significant data related to navigation equipment, other than specified in PBN/, as required by the appropriate ATS authority. Indicate GNSS augmentation under this indicator, with a space between two or more methods of augmentation. Example: NAV/GBAS SBAS.
COM/
Indicate communications applications or capabilities not specified in Item 10a.
DAT/
Indicate data applications or capabilities not specified in 10a.
SUR/
Include surveillance applications or capabilities not specified in Item 10b.
DEP/
Name and location of departure aerodrome, if ZZZZ is inserted in Item 13, or the ATS unit from which supplementary flight plan data can be obtained, if AFIL is inserted in Item 13. For aerodromes not listed in the relevant Aeronautical Information Publication, indicate location as follows:
-
With 4 figures describing latitude in degrees and tens and units of minutes followed by “N” (North) or “S” (South), followed by 5 figures describing longitude in degrees and tens and units of minutes, followed by “E” (East) or “W” (West). Make up the correct number of figures, where necessary, by insertion of zeros.
Example: DEP/ 4620N07805W (11 characters).
-
The identification of the significant point followed by the bearing from the point in the form of 3 figures giving degrees magnetic, followed by the distance from the point in the form of 3 figures expressing nautical miles. In areas of high latitude where it is determined by the appropriate authority that reference to degrees magnetic is impractical, degrees true may be used. Make up the correct number of figures, where necessary, by insertion of zeros. Example: A point of 180° magnetic at a distance of 40 nautical miles from “MLV” VOR should be expressed as: DEP/ MLV180040.
-
The first point of the route (name or LAT/LONG) or the marker radio beacon, if the aircraft has not taken off from an aerodrome.
DEST
/ Name and place of destination aerodrome, if ZZZZ is entered in item
16. For aerodromes not shown in the aeronautical information publication, enter the location in LAT/LONG or the bearing and distance from the nearest significant point as described above in DEP/ and RMK/ in plain text the name of the place of arrival.
DOF/
The date of flight departure in a six figure format (YYMMDD), where AA equals the year, MM equals the month and DD equals the
day).
Example: DOF/240430
REG/
The nationality or common mark and registration mark of the aircraft, if different from the aircraft identification in Item 7.
Example: REG/HCCKM
EET/
Significant points or FIR boundary designators and accumulated estimated elapsed times from take-off to such points or FIR boundaries, when so prescribed on the basis of regional air navigation agreements, or by the appropriate ATS
authority.
Example:
EET/SKED0015 MPZL0043.
SEL/
SELCAL Code, for aircraft so equipped.
Example: SEL/CKLM
TYP/
Type(s) of aircraft preceded if necessary without a space by number(s) of aircraft and separated by one space, if ZZZZ is inserted in Item 9.
Example:
TYP/J328 VNS41
CODE/
Aircraft address (expressed in the form of an alphanumerical code of six hexadecimal characters) when required by the appropriate ATS authority.
Example:
CODE/F00001
DLE
/ Delay or holding
en route: enter the significant points on the route where the delay is expected to occur, followed by the length of the delay using four-figure for the time in hours and minutes (hhmm).
Example: DLE/AND030
OPR/
ICAO designator or name of the aircraft operator, if different from the aircraft identification in item 7.
Example:
OPR/SAETA
ORGN/
The originator’s 8 letter AFTN address or other appropriate contact details, in cases where the originator of the flight plan may not be readily identified, as required by the appropriate ATS authority.
PER/
Aircraft performance data, indicated by a single letter as specified in the Procedures for Air Navigation Services - Aircraft Operations (PANSOPS, Doc 8168), Volume I - Flight Procedures, if so prescribed by the appropriate ATS authority.
Example:
PER/C
ALTN/
Name of destination alternate aerodrome(s), if ZZZZ is inserted in Item 16. For aerodromes not listed in the relevant Aeronautical Information Publication, indicate location in LAT/LONG or bearing and distance from the nearest significant point, as described in DEP/ above.
RALT/
ICAO four letter location indicator(s) for en-route alternate(s). For aerodromes not listed in the relevant Aeronautical Information Publication, indicate location in LAT/LONG or bearing and distance from the nearest significant point, as described in DEP/ above.
TALT/
ICAO four letter indicator(s) for take-off alternate as specified in Doc 7910. For aerodromes not listed in the relevant Aeronautical Information Publication, indicate location in LAT/LONG or bearing and distance from the nearest significant point, as described in DEP/above.
RIF/
The route details to the revised destination aerodrome followed by the ICAO four-letter location indicator of the aerodrome; the revised route is subject to re-clearance in flight.
Example:
RIF/DTA HEC KLAX
RIF/ESP G94 CLA YPPH
RMK/
Any other plain language remarks when required by the appropriate ATS authority, or if deemed necessary.
|
ITEM 19: SUPPLEMENTARY INFORMATION
|
|
|
E/ ENTER a 4-figure group, giving the fuel endurance in hours and minutes.
Example: 0430
|
|
|
P/ ENTER the total number of persons (passengers and crew) on board or TBN (to be notified) if the total number of persons is not known at the time of filing.
Example:
005 015 150
|
c.
Emergency and survival equipment
|
R/ (RADIO)
-
CROSS OUT U if UHF on frequency 243.0 MHz is not available;
-
CROSS OUT V if VHF on frequency 121.5 MHz is not available; or
-
CROSS OUT E if emergency locator transmitter (ELT) is not available.
S/ (Survival Equipment)
-
CROSS OUT all indicators, if the survival equipment is not carried, or
-
CROSS OUT one or more letters from the indicators of the equipment is not carried on board.
J/ (JACKETS)
-
CROSS OUT all indicators, if life jackets are not carried;
-
CROSS OUT L if life jackets are not equipped with lights;
-
CROSS OUT F if life jackets are not equipped with fluorescein;
-
CROSS OUT U or V or both as in R/ above to indicate radio capability of jackets, if any.
D/ (DINGHIES)
-
CROSS OUT indicators D and C if no dinghies are carried.
(NUMBER)
-
ENTER the number of dinghies carried.
(CAPACITY)
-
ENTER the total capacity, persons on board, of all dinghies carried.
(COVER)
-
CROSS OUT the indicator C if dinghies are not covered.
(COLOUR )
-
ENTER the colour of dinghies if carried.
A/ (AIRCRAFT COLOUR AND MARKINGS)
-
ENTER the colour of aircraft and significant markings.
N/ (REMARKS)
-
CROSS OUT the indicator N if no remarks, or indicate any other survival equipment carried and any other remarks regarding survival equipment.
C/ (PILOT, RESPONSIBLE NAME, LICENSE NUMBER AND SIGN)
a) Filed by
Enter the name of the unit, agency, or person submitting the flight plan.
b) DGAC
Registration Number
Enter the DGAC registration number of the person responsible for the filing of the Flight Plan, when not submitted by the pilot commander.
c) Signature
Signature of the person responsible for filing out the Flight Plan.
d) Flight plan acceptance
Indicate the acceptance of the flight plan in the form prescribed by the personnel of the appropriate AIS-AD Room or any other appropriate unit in case there is no AIS-AD room.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
5
ASSOCIATED FLIGHT PLAN MESSAGES
|
5.1
Modification Message (CHG)
|
When a change needs to be made to the flight plan, a CHG message will be transmitted. A CHG message will only be transmitted when there is a change in the basic data, except for:
-
Aircraft Identification.
-
Departure aerodrome.
-
Destination aerodrome.
-
Estimated off-block date
-
Estimated off-block time (*).
(*)
For any advance of 30 minutes in the EOBT, the previous flight plan must be canceled and a new one created; however, if the modification of the EOBT results in a delay compared to what was listed in the FPL, it will involve the transmission of a delay message (DLA). This applies as long as it is within the validity period of the flight plan or a maximum of 10 minutes before the expiration of the flight plan, whether it is IFR or VFR.
The CHG message will be sent to all flight plan data recipients affected by the change.
|
5.2
Cancellation Message (CNL)
|
After the submission and transmission of a
FPL, any modification in the following fields will generate a cancellation message (CNL) for the original FPL and the submission of a new one:
-
Aircraft Identification.
-
Departure aerodrome.
-
Destination aerodrome.
-
Estimated off-block date
-
Estimated off-block time (EOBT applies only in the case of an advance).
It is very important that the originator of a plan cancels this:
-
As soon as it is known that the flight will not operate, or
-
Before submitting a flight plan that will replace it.
-
Before the expiration of the validity time of the flight plan (minimum 30 before its operation)
|
|
|
In the event of a delay of more than 30 minutes from the estimated off-block time for a controlled flight, or one hour for an uncontrolled flight for which a flight plan has been submitted, the flight plan should be amended, or a new flight plan should be filed cancelling the old one, as appropriate. Before the expiration of the validity time of the flight plan.
Note 1
: Failure to properly notify a delay in departure of a controlled flight may result in the relevant flight plan data no longer being available to the appropriate ATS unit when a clearance is ultimately requested, resulting in additional flight delay.
Note 2
: Failure to properly notify a delayed departure (or cancellation) of a VFR flight from uncontrolled aerodromes may unnecessarily initiate an alert or search and rescue action when the flight does not arrive at the destination aerodrome within 30 minutes of its current ETA.
When a flight for which a flight plan has been submitted is cancelled, the appropriate ATS unit shall be informed immediately.
|
6
FLIGHT PLAN FORM FILING
|
The Flight Plan
forms must be filled out with
the prescribed formats and ways of filing, exactly as follows:
-
The data must be inserted in each of the Items, and when there is no information, it should be left empty, according to the formats established in this document.
-
The data shall be inserted in block letters and without corrections.
-
The time used shall be UTC (4 digits).
-
The expected flight time must be recorded in four digits (hours and minutes).
|
|
|
|
|